home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1994 March
/
Internet Info CD-ROM (Walnut Creek) (March 1994).iso
/
inet
/
internet-drafts
/
draft-ietf-decnetiv-mibextensions-02.txt
< prev
next >
Wrap
Text File
|
1993-03-03
|
2KB
|
58 lines
A new Request for Comments is now available in online RFC libraries.
RFC 1289:
Title: DECnet Phase IV MIB Extensions
Author: J. Saperia
Mailbox: saperia@enet.dec.com
Pages: 64
Characters: 122,272
Updates/Obsoletes: none
pathname: rfc/rfc1289.txt
This memo defines a set of DECnet Phase IV extensions that have been
created for the Internet MIB. When used in conjunction with the
structure of management information (RFC 1155), the management
information base for network management of TCP/IP-based internets (RFC
1213) and the Simple Network Management Protocol (RFC 1157), it will
be possible to provide integrated network management of combined
TCP/IP and DECnet Phase IV based internets. This document was
produced by the DECnet Phase IV MIB working group of the Internet
Engineering Task Force (IETF).
This memo is an extension to the SNMP MIB. This RFC specifies a
Proposed Standard Protocol for the Internet community, and requests
discussion and suggestions for improvements. Please refer to the
current edition of the "IAB Official Protocol Standards" for the
standardization state and status of this protocol. Distribution of
this memo is unlimited.
RFCs can be obtained via FTP from FTP.NISC.SRI.COM, NIS.NSF.NET,
NISC.JVNC.NET, VENERA.ISI.EDU, WUARCHIVE.WUSTL.EDU, or NIC.DDN.MIL.
Instructions for retrieving RFCs may be found in the file
"in-notes/rfc-retrieval.txt" on VENERA.ISI.EDU.
Requests to be added to or deleted from this distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to NIC@NIC.DDN.MIL. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
POSTEL@ISI.EDU. Please consult RFC 1111, "Instructions to RFC
Authors", for further information.
Joyce K. Reynolds
USC/Information Sciences Institute